Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d211c5b1202c2328af81e7f459afb4bc3a5ab3a75f3296cfd8956eeb612b5b9

Tx prefix hash: 6acc8ce104f74a38806fe5fd8866e983a9b6e64b6348ff18c9cdc485f5d49414
Tx public key: 7def5147cb57911b1b9b4d6fd0bce84b925258958943c4940770d24ad12eaff1
Timestamp: 1754307071 Timestamp [UCT]: 2025-08-04 11:31:11 Age [y:d:h:m:s]: 00:017:07:50:00
Block: 1340067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11412 RingCT/type: yes/0
Extra: 017def5147cb57911b1b9b4d6fd0bce84b925258958943c4940770d24ad12eaff1021100000001ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16cbe3ca57ef595f3893e6646ad9613e8ce42bc4de826de4d0c26819453a5e5e 0.600000000000 1827884 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": 1340077, "vin": [ { "gen": { "height": 1340067 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16cbe3ca57ef595f3893e6646ad9613e8ce42bc4de826de4d0c26819453a5e5e" } } ], "extra": [ 1, 125, 239, 81, 71, 203, 87, 145, 27, 27, 155, 77, 111, 208, 188, 232, 75, 146, 82, 88, 149, 137, 67, 196, 148, 7, 112, 210, 74, 209, 46, 175, 241, 2, 17, 0, 0, 0, 1, 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