Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e41bec588159d6939e4fae3ea8682c07316bd4a69905903c2e1ead849e750489

Tx prefix hash: 8415ea79032ac3484620318a303f8c62ff697beb02b14fdfbb12f8a17d5fdb7c
Tx public key: e66ac8f2a94a010efe39cbfdf1f24f16cb33fede5f3d4de20b91754bb06ed67a
Timestamp: 1723605703 Timestamp [UCT]: 2024-08-14 03:21:43 Age [y:d:h:m:s]: 00:239:19:42:25
Block: 1087446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171280 RingCT/type: yes/0
Extra: 01e66ac8f2a94a010efe39cbfdf1f24f16cb33fede5f3d4de20b91754bb06ed67a021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd2f08aee19000580d72f1e9ca8b033694aa2bc31cdfaf83a9cef117ad5d1e6e 0.600000000000 1562055 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": 1087456, "vin": [ { "gen": { "height": 1087446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd2f08aee19000580d72f1e9ca8b033694aa2bc31cdfaf83a9cef117ad5d1e6e" } } ], "extra": [ 1, 230, 106, 200, 242, 169, 74, 1, 14, 254, 57, 203, 253, 241, 242, 79, 22, 203, 51, 254, 222, 95, 61, 77, 226, 11, 145, 117, 75, 176, 110, 214, 122, 2, 17, 0, 0, 0, 2, 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