Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d31500ae685865c38de794d7825d59ca06ddd2a37ea44f18cb93a57a3f64634

Tx prefix hash: 6b7da6fdf70cca93728fb407fc7c1b7e6809162a43e387f3fe3372bd6446c4e6
Tx public key: b3b7515850f77160788ce8c89ae39532052e559248c0e23a5ef6a37c0b5ebcf5
Timestamp: 1686060954 Timestamp [UCT]: 2023-06-06 14:15:54 Age [y:d:h:m:s]: 01:306:21:49:15
Block: 776434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 480528 RingCT/type: yes/0
Extra: 01b3b7515850f77160788ce8c89ae39532052e559248c0e23a5ef6a37c0b5ebcf502110000000275e3f0e9000000000000000000

1 output(s) for total of 1.641920062000 dcy

stealth address amount amount idx
00: 32c1d2b90169ed9206df5ed1872e789408c735180ea6b3b8debce2a50d9a3575 1.641920062000 1225985 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": 776444, "vin": [ { "gen": { "height": 776434 } } ], "vout": [ { "amount": 1641920062, "target": { "key": "32c1d2b90169ed9206df5ed1872e789408c735180ea6b3b8debce2a50d9a3575" } } ], "extra": [ 1, 179, 183, 81, 88, 80, 247, 113, 96, 120, 140, 232, 200, 154, 227, 149, 50, 5, 46, 85, 146, 72, 192, 226, 58, 94, 246, 163, 124, 11, 94, 188, 245, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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