Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18bd3924cdeef3210a7024e37e23c9f4b440c1f3cfc7b202e616f577ffd275b8

Tx prefix hash: 3fe6a5bdb60919989f0644a1b0b02ee2cc458058df2f7e8f243e09fade525d0f
Tx public key: c3ac2b590d33be77aa0c5efbaa0ac09bf00195e804b14ec9f8ffb31f08204d8b
Timestamp: 1711368650 Timestamp [UCT]: 2024-03-25 12:10:50 Age [y:d:h:m:s]: 01:010:15:19:02
Block: 986024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268542 RingCT/type: yes/0
Extra: 01c3ac2b590d33be77aa0c5efbaa0ac09bf00195e804b14ec9f8ffb31f08204d8b0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3175a978060d730553537256d62900999164ac1d96b93e4ba4beaba743c32b9a 0.600000000000 1446249 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": 986034, "vin": [ { "gen": { "height": 986024 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3175a978060d730553537256d62900999164ac1d96b93e4ba4beaba743c32b9a" } } ], "extra": [ 1, 195, 172, 43, 89, 13, 51, 190, 119, 170, 12, 94, 251, 170, 10, 192, 155, 240, 1, 149, 232, 4, 177, 78, 201, 248, 255, 179, 31, 8, 32, 77, 139, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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