Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 342ea2f4b3b77a34791fe3c168e0589489807965267f28fb6a5af8b8d61d3be1

Tx prefix hash: effdb365754933e950c44bdfdc3d61b818393cf1b7f5becad3434885ed531a6f
Tx public key: 1578824db0de0ff7733541a3f1ebe4014fa8e09a9bdc0dfd3c4e832916d44d27
Timestamp: 1629335902 Timestamp [UCT]: 2021-08-19 01:18:22 Age [y:d:h:m:s]: 03:090:03:09:40
Block: 316762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 837970 RingCT/type: yes/0
Extra: 011578824db0de0ff7733541a3f1ebe4014fa8e09a9bdc0dfd3c4e832916d44d2702110000000458045e5b000000000000000000

1 output(s) for total of 54.756599005000 dcy

stealth address amount amount idx
00: a589bac5a6ff06cd89a427790dfe121a7402fc78085cc77a5688ecf887e8e66c 54.756599005000 658879 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": 316772, "vin": [ { "gen": { "height": 316762 } } ], "vout": [ { "amount": 54756599005, "target": { "key": "a589bac5a6ff06cd89a427790dfe121a7402fc78085cc77a5688ecf887e8e66c" } } ], "extra": [ 1, 21, 120, 130, 77, 176, 222, 15, 247, 115, 53, 65, 163, 241, 235, 228, 1, 79, 168, 224, 154, 155, 220, 13, 253, 60, 78, 131, 41, 22, 212, 77, 39, 2, 17, 0, 0, 0, 4, 88, 4, 94, 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