Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0b1fc104a014d178f6591d42f39fea66d0f4ca5e0e61eecb5141482c4165305

Tx prefix hash: 41ef4e18fc17c59ee8ae8f14e1778adffcd2ff1a2faeeb15135b851fb6834ed1
Tx public key: 39e985d198f1e358f90c9e6f1a96b1d76b2f4d814bdcc9695c753736dc7c09be
Timestamp: 1746290630 Timestamp [UCT]: 2025-05-03 16:43:50 Age [y:d:h:m:s]: 00:202:07:37:45
Block: 1274990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142315 RingCT/type: yes/0
Extra: 0139e985d198f1e358f90c9e6f1a96b1d76b2f4d814bdcc9695c753736dc7c09be0211000000069f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b7f92a0b6bf69b25d458fa457730394c331a0fdda1230504e4fa2f40dae5cd1 0.600000000000 1762293 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": 1275000, "vin": [ { "gen": { "height": 1274990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b7f92a0b6bf69b25d458fa457730394c331a0fdda1230504e4fa2f40dae5cd1" } } ], "extra": [ 1, 57, 233, 133, 209, 152, 241, 227, 88, 249, 12, 158, 111, 26, 150, 177, 215, 107, 47, 77, 129, 75, 220, 201, 105, 92, 117, 55, 54, 220, 124, 9, 190, 2, 17, 0, 0, 0, 6, 159, 159, 230, 140, 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