Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ea963ea289658f6c6a843dbd5c6d044283eee1c25be18e0d34e9c89baff3c34

Tx prefix hash: 7085783daccb9f4786551f8e2a7cc46a17160066d6b1687d27de0281b0303b3a
Tx public key: dce5823e506e3e158b5ce00f00c231d893d725cf90a75ea3f2627f21c007e655
Timestamp: 1714568548 Timestamp [UCT]: 2024-05-01 13:02:28 Age [y:d:h:m:s]: 00:318:10:21:19
Block: 1012528 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227647 RingCT/type: yes/0
Extra: 01dce5823e506e3e158b5ce00f00c231d893d725cf90a75ea3f2627f21c007e65502110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36188ac85c2cf4f5dc887cd81e3d9ca80661b5277a3c5427bca836e8348da2ae 0.600000000000 1475086 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": 1012538, "vin": [ { "gen": { "height": 1012528 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36188ac85c2cf4f5dc887cd81e3d9ca80661b5277a3c5427bca836e8348da2ae" } } ], "extra": [ 1, 220, 229, 130, 62, 80, 110, 62, 21, 139, 92, 224, 15, 0, 194, 49, 216, 147, 215, 37, 207, 144, 167, 94, 163, 242, 98, 127, 33, 192, 7, 230, 85, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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