Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97a1d5922c01a2b9a3f2a7ce1ac86b9484f812f8b87f7527954a0902ce556023

Tx prefix hash: bb8a899104d2e6891f814646081d41a28994e4414da1c06c842ca37e1162f12c
Tx public key: 861995ae63869f3c21cf05afd782afe3b9573015b849e6dd228b5335f2fb39cb
Timestamp: 1727224337 Timestamp [UCT]: 2024-09-25 00:32:17 Age [y:d:h:m:s]: 00:216:08:52:02
Block: 1117445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154479 RingCT/type: yes/0
Extra: 01861995ae63869f3c21cf05afd782afe3b9573015b849e6dd228b5335f2fb39cb02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70e448362d1a12e07aa7d2cabc5e97fd2ae8990fe8858ed60a3f64fb70ea39b7 0.600000000000 1598288 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": 1117455, "vin": [ { "gen": { "height": 1117445 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70e448362d1a12e07aa7d2cabc5e97fd2ae8990fe8858ed60a3f64fb70ea39b7" } } ], "extra": [ 1, 134, 25, 149, 174, 99, 134, 159, 60, 33, 207, 5, 175, 215, 130, 175, 227, 185, 87, 48, 21, 184, 73, 230, 221, 34, 139, 83, 53, 242, 251, 57, 203, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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