Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2e72ebc062ba0a8d9c4e52e47f3746fd208c1ccb7c25305896c34def93ebb3b

Tx prefix hash: e67c5b6714eed51827fc3838e52821cc43dfd0d0d7ebf99019c285256da17e26
Tx public key: 7eada94fbd1e1a06c78dd2ce67a70fc4df41104f00e70430e52ded3f69f7a03d
Timestamp: 1757905707 Timestamp [UCT]: 2025-09-15 03:08:27 Age [y:d:h:m:s]: 00:074:06:53:55
Block: 1368700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53195 RingCT/type: yes/0
Extra: 017eada94fbd1e1a06c78dd2ce67a70fc4df41104f00e70430e52ded3f69f7a03d021100000003b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51831bdc86248e1cddb35458ff6594a6224f2862c41f3e5c368dc637868136af 0.600000000000 1856751 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": 1368710, "vin": [ { "gen": { "height": 1368700 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51831bdc86248e1cddb35458ff6594a6224f2862c41f3e5c368dc637868136af" } } ], "extra": [ 1, 126, 173, 169, 79, 189, 30, 26, 6, 199, 141, 210, 206, 103, 167, 15, 196, 223, 65, 16, 79, 0, 231, 4, 48, 229, 45, 237, 63, 105, 247, 160, 61, 2, 17, 0, 0, 0, 3, 178, 247, 132, 196, 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