Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bc5ad4f363f51a0a038f4888eeb6af4658302e1091705879aebbf9b3f93b8a8

Tx prefix hash: 7eb1d8c35075c7321f568fec74a20a9fc17b53dcba2c08a594d3bf8e94ceb077
Tx public key: b60874f055d7f3c57ed03a7023518669c7a98e8c5feb655e6aefb136e2f4af27
Timestamp: 1726848975 Timestamp [UCT]: 2024-09-20 16:16:15 Age [y:d:h:m:s]: 00:217:08:05:59
Block: 1114335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155147 RingCT/type: yes/0
Extra: 01b60874f055d7f3c57ed03a7023518669c7a98e8c5feb655e6aefb136e2f4af27021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 553e973eb45c0c052e430a5a3c395fce3c04a41e07a29b50e6abf394feb132e6 0.600000000000 1594136 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": 1114345, "vin": [ { "gen": { "height": 1114335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "553e973eb45c0c052e430a5a3c395fce3c04a41e07a29b50e6abf394feb132e6" } } ], "extra": [ 1, 182, 8, 116, 240, 85, 215, 243, 197, 126, 208, 58, 112, 35, 81, 134, 105, 199, 169, 142, 140, 95, 235, 101, 94, 106, 239, 177, 54, 226, 244, 175, 39, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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