Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5b038f3a0d85f4a2be569ab4cba776dc175bf6916967302d8f6e253ca624fce

Tx prefix hash: a39a4ac725e4609e76f2551b84a8f1e46a9a9b3af652bb588a4630f8bc1d1f87
Tx public key: e3c5a0bce9a77a94f6be27046944b2365b148d88b200b52bc989bcc18eccd9c3
Timestamp: 1727493344 Timestamp [UCT]: 2024-09-28 03:15:44 Age [y:d:h:m:s]: 00:184:02:03:21
Block: 1119682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131364 RingCT/type: yes/0
Extra: 01e3c5a0bce9a77a94f6be27046944b2365b148d88b200b52bc989bcc18eccd9c302110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91eb5d0a34c33b5c87111fd361ff883fcbe7db0cc10ad43bb2e83321da05818c 0.600000000000 1601329 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": 1119692, "vin": [ { "gen": { "height": 1119682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91eb5d0a34c33b5c87111fd361ff883fcbe7db0cc10ad43bb2e83321da05818c" } } ], "extra": [ 1, 227, 197, 160, 188, 233, 167, 122, 148, 246, 190, 39, 4, 105, 68, 178, 54, 91, 20, 141, 136, 178, 0, 181, 43, 201, 137, 188, 193, 142, 204, 217, 195, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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