Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ea3bf6b79f3616169054d28301a147def2b04d28cd4aaa9795d4f83d9d21418

Tx prefix hash: adcef87f7be4d07414cd5bfe800c98e42c8438b880d0b791815c080c2bf9cddd
Tx public key: 15a6771d25239d27611f99bdac5f4f7e3ab2680e7ab8ba72ed8d7cabef89bda3
Timestamp: 1738975109 Timestamp [UCT]: 2025-02-08 00:38:29 Age [y:d:h:m:s]: 00:336:18:04:10
Block: 1214440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238517 RingCT/type: yes/0
Extra: 0115a6771d25239d27611f99bdac5f4f7e3ab2680e7ab8ba72ed8d7cabef89bda302110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 739009c6b117deb45557a6987b8e1d22131ca81fa16ac2c8d032d6ab689f4363 0.600000000000 1701231 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": 1214450, "vin": [ { "gen": { "height": 1214440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "739009c6b117deb45557a6987b8e1d22131ca81fa16ac2c8d032d6ab689f4363" } } ], "extra": [ 1, 21, 166, 119, 29, 37, 35, 157, 39, 97, 31, 153, 189, 172, 95, 79, 126, 58, 178, 104, 14, 122, 184, 186, 114, 237, 141, 124, 171, 239, 137, 189, 163, 2, 17, 0, 0, 0, 12, 0, 127, 151, 138, 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