Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 089b913f1161409e75912a11df93b5b70f53d57030f6de102c4e12c7828bdd79

Tx prefix hash: 175e0f0337f7c152c75a138eb7e200e9823496b66e515f15408937e42c574b51
Tx public key: c34b2265eae8c92a3effa95be48254786411d68cc37802dc093d41b3f29cbc4b
Timestamp: 1713797358 Timestamp [UCT]: 2024-04-22 14:49:18 Age [y:d:h:m:s]: 01:056:00:02:58
Block: 1006132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300881 RingCT/type: yes/0
Extra: 01c34b2265eae8c92a3effa95be48254786411d68cc37802dc093d41b3f29cbc4b02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae702b6fb194635784c639f1d93d0fb091f7ffbe5cdd6d6312dc53d6885e7c6e 0.600000000000 1467058 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": 1006142, "vin": [ { "gen": { "height": 1006132 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae702b6fb194635784c639f1d93d0fb091f7ffbe5cdd6d6312dc53d6885e7c6e" } } ], "extra": [ 1, 195, 75, 34, 101, 234, 232, 201, 42, 62, 255, 169, 91, 228, 130, 84, 120, 100, 17, 214, 140, 195, 120, 2, 220, 9, 61, 65, 179, 242, 156, 188, 75, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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