Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5eedf44e17317fde1ee6d3139777d694859c4ba856e81cc9f38b4790cbf3644f

Tx prefix hash: 811ea3282c28c59a65ebb97c973c15f1a74fa8d59d5c6abcc1471e5e1147ac1e
Tx public key: cb72453e6f163daee9f53fd83e961192ea732a57ca0af70d00a8a80045fa4d6e
Timestamp: 1753875601 Timestamp [UCT]: 2025-07-30 11:40:01 Age [y:d:h:m:s]: 00:018:07:13:34
Block: 1336620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12059 RingCT/type: yes/0
Extra: 01cb72453e6f163daee9f53fd83e961192ea732a57ca0af70d00a8a80045fa4d6e021100000005ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07ab3ec9f783f61a8041ef6fa2e703a5cf7f66cc71f37370a531c92e008dfa6c 0.600000000000 1824421 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": 1336630, "vin": [ { "gen": { "height": 1336620 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07ab3ec9f783f61a8041ef6fa2e703a5cf7f66cc71f37370a531c92e008dfa6c" } } ], "extra": [ 1, 203, 114, 69, 62, 111, 22, 61, 174, 233, 245, 63, 216, 62, 150, 17, 146, 234, 115, 42, 87, 202, 10, 247, 13, 0, 168, 168, 0, 69, 250, 77, 110, 2, 17, 0, 0, 0, 5, 173, 121, 72, 208, 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