Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d56c394babac2d6ae03ff7eec4890a3027218bfe00ec0136ff7b6ec0ad50b68

Tx prefix hash: 665660b6c6d7d1bee596c2d2f4ae3097377e57add004379e21e5c2c818f87173
Tx public key: a6b2fd8f23f30d322b9f20fff375660ff2f7837b941f872338259211f44fecaa
Timestamp: 1749557346 Timestamp [UCT]: 2025-06-10 12:09:06 Age [y:d:h:m:s]: 00:152:09:55:21
Block: 1302057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106600 RingCT/type: yes/0
Extra: 01a6b2fd8f23f30d322b9f20fff375660ff2f7837b941f872338259211f44fecaa021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5bd8ca8cccef4fee268e45213876bc65c04a36849f5ed60d34804036fed1a7c 0.600000000000 1789626 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": 1302067, "vin": [ { "gen": { "height": 1302057 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5bd8ca8cccef4fee268e45213876bc65c04a36849f5ed60d34804036fed1a7c" } } ], "extra": [ 1, 166, 178, 253, 143, 35, 243, 13, 50, 43, 159, 32, 255, 243, 117, 102, 15, 242, 247, 131, 123, 148, 31, 135, 35, 56, 37, 146, 17, 244, 79, 236, 170, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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