Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1a2c4a878ac4683bb58fb44ae8fa8e702401f4d4b0488491aa14def31165ae2

Tx prefix hash: 8f86e7810ae35d2535a4f7f6751bf900c3436b567efc31fdd0d64d23f2d055b8
Tx public key: e7eb5ba7f78630fc501a3af8ca56c230952e228c1438ad207e4eee60cae39801
Timestamp: 1689543967 Timestamp [UCT]: 2023-07-16 21:46:07 Age [y:d:h:m:s]: 01:186:15:24:44
Block: 805324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394742 RingCT/type: yes/0
Extra: 01e7eb5ba7f78630fc501a3af8ca56c230952e228c1438ad207e4eee60cae3980102110000000675e3f0e9000000000000000000

1 output(s) for total of 1.317126247000 dcy

stealth address amount amount idx
00: de8d819bcc3cfec408baa0a7402992e0d06f34433c5704fa8eb33ca562bb8fca 1.317126247000 1256549 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": 805334, "vin": [ { "gen": { "height": 805324 } } ], "vout": [ { "amount": 1317126247, "target": { "key": "de8d819bcc3cfec408baa0a7402992e0d06f34433c5704fa8eb33ca562bb8fca" } } ], "extra": [ 1, 231, 235, 91, 167, 247, 134, 48, 252, 80, 26, 58, 248, 202, 86, 194, 48, 149, 46, 34, 140, 20, 56, 173, 32, 126, 78, 238, 96, 202, 227, 152, 1, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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