Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87f1206052a972e146863cce4df5e98c6edcdadcf343e6fb715de6cd4c9c90a5

Tx prefix hash: d3ed94f2051aea51bc79a1a670dce62a29d6b1a780385dbdb46387c61438a0a0
Tx public key: bd46dc178322a598e8dcece3f360be9cd39ed6dc634576589d20ccb7a97e29cc
Timestamp: 1694858401 Timestamp [UCT]: 2023-09-16 10:00:01 Age [y:d:h:m:s]: 01:129:10:59:10
Block: 849301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353798 RingCT/type: yes/0
Extra: 01bd46dc178322a598e8dcece3f360be9cd39ed6dc634576589d20ccb7a97e29cc0211000000054b8f5122000000000000000000

1 output(s) for total of 0.941701545000 dcy

stealth address amount amount idx
00: 4b12c350eb33655732a449a52e1f31725d7514150def8cc0a840a6e2fcedf650 0.941701545000 1302959 of 0

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": 849311, "vin": [ { "gen": { "height": 849301 } } ], "vout": [ { "amount": 941701545, "target": { "key": "4b12c350eb33655732a449a52e1f31725d7514150def8cc0a840a6e2fcedf650" } } ], "extra": [ 1, 189, 70, 220, 23, 131, 34, 165, 152, 232, 220, 236, 227, 243, 96, 190, 156, 211, 158, 214, 220, 99, 69, 118, 88, 157, 32, 204, 183, 169, 126, 41, 204, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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