Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: b6484dc6c58eae39bdeb6225fc6fd9fa5cb3f9088f1c5b78b135fcb45261feeb

Tx prefix hash: ca1d0901552b861ed1f54dc84c13d38917a27407f822ce415c2a18ccdea35135
Tx public key: 492aec628aed9aa77007e21944f98ffd1205562e012a817217b33098a2b30dd9
Timestamp: 1708646093 Timestamp [UCT]: 2024-02-22 23:54:53 Age [y:d:h:m:s]: 01:304:20:36:22
Block: 963425 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476675 RingCT/type: yes/0
Extra: 01492aec628aed9aa77007e21944f98ffd1205562e012a817217b33098a2b30dd902110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd3dd8befc6736ea3cbfe28d853c300e1e9a73b66a382a84ee692a8904761b5c 0.600000000000 1423136 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 963435, "vin": [ { "gen": { "height": 963425 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd3dd8befc6736ea3cbfe28d853c300e1e9a73b66a382a84ee692a8904761b5c" } } ], "extra": [ 1, 73, 42, 236, 98, 138, 237, 154, 167, 112, 7, 226, 25, 68, 249, 143, 253, 18, 5, 86, 46, 1, 42, 129, 114, 23, 179, 48, 152, 162, 179, 13, 217, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8