Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 786b3a22fc25a27a7af9ae867b534804eb4ed305f52e05bdb400ccdc43c780ad

Tx prefix hash: d1dc6499a554e1626d25773ff311022f901070c70eabe14daf43b2d5285b9f17
Tx public key: 250e7188ce000248dbb47548cd7ed737eb32ee51b4ea1f21726ea3a36f6c69f3
Timestamp: 1730668201 Timestamp [UCT]: 2024-11-03 21:10:01 Age [y:d:h:m:s]: 00:154:21:58:31
Block: 1145915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110543 RingCT/type: yes/0
Extra: 01250e7188ce000248dbb47548cd7ed737eb32ee51b4ea1f21726ea3a36f6c69f3021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8045f75250f58c6c5e4c7d1f153ecf968e201b86eefd1fe0f5e4ddb0aa9a13c 0.600000000000 1630444 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": 1145925, "vin": [ { "gen": { "height": 1145915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8045f75250f58c6c5e4c7d1f153ecf968e201b86eefd1fe0f5e4ddb0aa9a13c" } } ], "extra": [ 1, 37, 14, 113, 136, 206, 0, 2, 72, 219, 180, 117, 72, 205, 126, 215, 55, 235, 50, 238, 81, 180, 234, 31, 33, 114, 110, 163, 163, 111, 108, 105, 243, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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