Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebbfe915570a85158cf2577aeadf33ec9fe1a583d27ceabbdc4bb10ee0007b3b

Tx prefix hash: c7b7306e8b98ae172bf306b9c5b937e4ea6fc854a32b1d57330c9143b17e112f
Tx public key: 1d82a4b0f6d9289b3c42cd03d0cd3cf95082bd33efcdaa32d268e91b86ee2528
Timestamp: 1754291312 Timestamp [UCT]: 2025-08-04 07:08:32 Age [y:d:h:m:s]: 00:013:11:18:15
Block: 1339939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8733 RingCT/type: yes/0
Extra: 011d82a4b0f6d9289b3c42cd03d0cd3cf95082bd33efcdaa32d268e91b86ee2528021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e617847c6740069a7be01f26bf5d25feb639ae9a76a84ad8317c2909f601080 0.600000000000 1827754 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": 1339949, "vin": [ { "gen": { "height": 1339939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e617847c6740069a7be01f26bf5d25feb639ae9a76a84ad8317c2909f601080" } } ], "extra": [ 1, 29, 130, 164, 176, 246, 217, 40, 155, 60, 66, 205, 3, 208, 205, 60, 249, 80, 130, 189, 51, 239, 205, 170, 50, 210, 104, 233, 27, 134, 238, 37, 40, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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