Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 062dcee6e00ab6176cf9c788f24e5865d118e5a69deeef43e496e27012669032

Tx prefix hash: 6efb7b1c8a01471a68c4031026edc8300a5a1375483db9ce86d38832f69738fc
Tx public key: c72e2939cb459e0a823f6e42a234f816be4873f766dc737308ff4479ea6d8f1b
Timestamp: 1727456291 Timestamp [UCT]: 2024-09-27 16:58:11 Age [y:d:h:m:s]: 00:231:06:15:39
Block: 1119373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165106 RingCT/type: yes/0
Extra: 01c72e2939cb459e0a823f6e42a234f816be4873f766dc737308ff4479ea6d8f1b021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3960bf29c1afedbe4a46f2baf74adbfd09d4a6da5098265574c2ae72789acd04 0.600000000000 1600908 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": 1119383, "vin": [ { "gen": { "height": 1119373 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3960bf29c1afedbe4a46f2baf74adbfd09d4a6da5098265574c2ae72789acd04" } } ], "extra": [ 1, 199, 46, 41, 57, 203, 69, 158, 10, 130, 63, 110, 66, 162, 52, 248, 22, 190, 72, 115, 247, 102, 220, 115, 115, 8, 255, 68, 121, 234, 109, 143, 27, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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