Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de36333c118262d1925aa09243ed63dd1c3c151d1e57ba66784564db3b4e4c9b

Tx prefix hash: bcb06d271a186ff2b04781c95497f142d02f10c794628cd1d3489b6bfa8b62c5
Tx public key: d12046fae51d8df7165293f64b44c51b2ce993d30a85d96e6b48ef44a31db94f
Timestamp: 1740868591 Timestamp [UCT]: 2025-03-01 22:36:31 Age [y:d:h:m:s]: 00:333:15:16:35
Block: 1230099 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236116 RingCT/type: yes/0
Extra: 01d12046fae51d8df7165293f64b44c51b2ce993d30a85d96e6b48ef44a31db94f021100000019007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ad0f8195640491536038d5680a9a9e60c586731f6db9ba351b4e340e29eddcf 0.600000000000 1716994 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": 1230109, "vin": [ { "gen": { "height": 1230099 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ad0f8195640491536038d5680a9a9e60c586731f6db9ba351b4e340e29eddcf" } } ], "extra": [ 1, 209, 32, 70, 250, 229, 29, 141, 247, 22, 82, 147, 246, 75, 68, 197, 27, 44, 233, 147, 211, 10, 133, 217, 110, 107, 72, 239, 68, 163, 29, 185, 79, 2, 17, 0, 0, 0, 25, 0, 127, 151, 138, 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