Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1715fd5c4f2d7eb0bdac86da3e439f747de494b4f943bf125bb029d7367d4248

Tx prefix hash: ad4f1b22e777938b031ebcdc276c523d39a3b822c5a67c58cb6be05c90853d74
Tx public key: b5c0d19fcbe3125e21303e9075e83811bed03971d4a588b3890987e90652face
Timestamp: 1734966358 Timestamp [UCT]: 2024-12-23 15:05:58 Age [y:d:h:m:s]: 00:100:00:34:41
Block: 1181540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71253 RingCT/type: yes/0
Extra: 01b5c0d19fcbe3125e21303e9075e83811bed03971d4a588b3890987e90652face0211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5df4abd7c092619775f0a82a6bb9b3a6a7d510d6e499615f524d815e03110587 0.600000000000 1667965 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": 1181550, "vin": [ { "gen": { "height": 1181540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5df4abd7c092619775f0a82a6bb9b3a6a7d510d6e499615f524d815e03110587" } } ], "extra": [ 1, 181, 192, 209, 159, 203, 227, 18, 94, 33, 48, 62, 144, 117, 232, 56, 17, 190, 208, 57, 113, 212, 165, 136, 179, 137, 9, 135, 233, 6, 82, 250, 206, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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