Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e333384a9913a7eff20669b27387101bc65ae61ed58d8f6c47e442325d6bf05

Tx prefix hash: 87dc3953266c2f4a514bbf13b81c544432d7df7ba2a1d84c407619e67265857f
Tx public key: 6b9d30d3bf2bf764b7e9a6b2415da639e30c897e40be3b9404b5530feba416d5
Timestamp: 1745640254 Timestamp [UCT]: 2025-04-26 04:04:14 Age [y:d:h:m:s]: 00:015:15:10:05
Block: 1269605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11186 RingCT/type: yes/0
Extra: 016b9d30d3bf2bf764b7e9a6b2415da639e30c897e40be3b9404b5530feba416d502110000000401491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66b4e475f581ab2265e0eafd585cebd9f6904c70dd31e80ec42749dbe9a4d278 0.600000000000 1756844 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": 1269615, "vin": [ { "gen": { "height": 1269605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66b4e475f581ab2265e0eafd585cebd9f6904c70dd31e80ec42749dbe9a4d278" } } ], "extra": [ 1, 107, 157, 48, 211, 191, 43, 247, 100, 183, 233, 166, 178, 65, 93, 166, 57, 227, 12, 137, 126, 64, 190, 59, 148, 4, 181, 83, 15, 235, 164, 22, 213, 2, 17, 0, 0, 0, 4, 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