Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e421c114cdeb0b5279878830fcff23462e819f3b84bfeb590cca1f59f0ea01c6

Tx prefix hash: e718b2a900a5d01e171782b4b14dd4a2c254a3a8e058abcfdf5c98e48c7ecb09
Tx public key: 7d39e9c5f0958fb5cf00d3b9a8ca0adf7efcd8409350631c630b7fde10f2a931
Timestamp: 1763983216 Timestamp [UCT]: 2025-11-24 11:20:16 Age [y:d:h:m:s]: 00:002:22:59:11
Block: 1419067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2122 RingCT/type: yes/0
Extra: 017d39e9c5f0958fb5cf00d3b9a8ca0adf7efcd8409350631c630b7fde10f2a9310211000000018ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84d62bf2c93310d9e7aac72e5a66f3a857b621edbf5d23e2d6ebb18e6e04bae1 0.600000000000 1907602 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": 1419077, "vin": [ { "gen": { "height": 1419067 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84d62bf2c93310d9e7aac72e5a66f3a857b621edbf5d23e2d6ebb18e6e04bae1" } } ], "extra": [ 1, 125, 57, 233, 197, 240, 149, 143, 181, 207, 0, 211, 185, 168, 202, 10, 223, 126, 252, 216, 64, 147, 80, 99, 28, 99, 11, 127, 222, 16, 242, 169, 49, 2, 17, 0, 0, 0, 1, 140, 235, 127, 9, 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