Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec80fb74aab2e57b62ddf0ea097072ccaf1422119a45402d7f8da4ad7aa1d66c

Tx prefix hash: 2f99cec0d1b4e68f69a6a75b2e8c6b9920f40661be79a334887d42289cf745e7
Tx public key: 952705c9659c0ee58d797cc072d5575058e8da6e14f9e6b288260e302369be87
Timestamp: 1738215660 Timestamp [UCT]: 2025-01-30 05:41:00 Age [y:d:h:m:s]: 00:138:00:32:57
Block: 1208152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98610 RingCT/type: yes/0
Extra: 01952705c9659c0ee58d797cc072d5575058e8da6e14f9e6b288260e302369be87021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b713ba9b3a5b78c808f5a0b884dae3ad7a7df5ede4e23343c276825b66f4ac6 0.600000000000 1694881 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": 1208162, "vin": [ { "gen": { "height": 1208152 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b713ba9b3a5b78c808f5a0b884dae3ad7a7df5ede4e23343c276825b66f4ac6" } } ], "extra": [ 1, 149, 39, 5, 201, 101, 156, 14, 229, 141, 121, 124, 192, 114, 213, 87, 80, 88, 232, 218, 110, 20, 249, 230, 178, 136, 38, 14, 48, 35, 105, 190, 135, 2, 17, 0, 0, 0, 1, 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