Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e17a2edafd3d44d3b8edcab9a98e3a2e7c3af9e89a713a6c425fafa807db4171

Tx prefix hash: e91a776519d2a82097f9bba7fca2326aba15d2d10fb470acf7e018331bcf8330
Tx public key: 3d5d107ca33a6a2541729ed63511801ee835a693b459d4b353ff6015bc15de7c
Timestamp: 1695956121 Timestamp [UCT]: 2023-09-29 02:55:21 Age [y:d:h:m:s]: 01:108:21:04:53
Block: 858426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339076 RingCT/type: yes/0
Extra: 013d5d107ca33a6a2541729ed63511801ee835a693b459d4b353ff6015bc15de7c02110000000233af99f4000000000000000000

1 output(s) for total of 0.878371744000 dcy

stealth address amount amount idx
00: 6eecdd627212cee99adc53db1f178491ad8c28070d40c48c1a248346e716cbc1 0.878371744000 1312600 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": 858436, "vin": [ { "gen": { "height": 858426 } } ], "vout": [ { "amount": 878371744, "target": { "key": "6eecdd627212cee99adc53db1f178491ad8c28070d40c48c1a248346e716cbc1" } } ], "extra": [ 1, 61, 93, 16, 124, 163, 58, 106, 37, 65, 114, 158, 214, 53, 17, 128, 30, 232, 53, 166, 147, 180, 89, 212, 179, 83, 255, 96, 21, 188, 21, 222, 124, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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