Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c44881eda7b85d443d14a0abfc809edb9f9c87039cc1856ea116060f1d7bc6d0

Tx prefix hash: ee163c831d41584298292eb5642a989f4041bcf9f7d6b725fa373165a8715c6e
Tx public key: 27824c5a297f2cecbb5ae55c1b7737bdf3c4138c195ab74e820e121eadd2c3fb
Timestamp: 1754326377 Timestamp [UCT]: 2025-08-04 16:52:57 Age [y:d:h:m:s]: 00:017:01:40:24
Block: 1340213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11235 RingCT/type: yes/0
Extra: 0127824c5a297f2cecbb5ae55c1b7737bdf3c4138c195ab74e820e121eadd2c3fb02110000000301491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40739f83e9143981b1c9559031118324e5b6d0648f2132ae041a0e5320b336c4 0.600000000000 1828030 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": 1340223, "vin": [ { "gen": { "height": 1340213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40739f83e9143981b1c9559031118324e5b6d0648f2132ae041a0e5320b336c4" } } ], "extra": [ 1, 39, 130, 76, 90, 41, 127, 44, 236, 187, 90, 229, 92, 27, 119, 55, 189, 243, 196, 19, 140, 25, 90, 183, 78, 130, 14, 18, 30, 173, 210, 195, 251, 2, 17, 0, 0, 0, 3, 1, 73, 31, 136, 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