Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1eff41064fefea6926944aae579631dc5a53146441ab9ad8468c54ac87041ef5

Tx prefix hash: 6e37db015d5eccf8f0cfdd77f748da0c2ba1254d6136e9242cac46ec07db1abf
Tx public key: 93b99941ae96bafdfbd6a84480cad1298d74c890f8a0985ad826d5b0b2400d5c
Timestamp: 1638410543 Timestamp [UCT]: 2021-12-02 02:02:23 Age [y:d:h:m:s]: 03:103:13:48:36
Block: 386492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 852736 RingCT/type: yes/0
Extra: 0193b99941ae96bafdfbd6a84480cad1298d74c890f8a0985ad826d5b0b2400d5c021100000011f6cc1430000000000000000000

1 output(s) for total of 32.165620578000 dcy

stealth address amount amount idx
00: 1cbe6f5a21858a8d40778893611695e2bf51d5f78e6b3882b6f2af525de53fe1 32.165620578000 779731 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": 386502, "vin": [ { "gen": { "height": 386492 } } ], "vout": [ { "amount": 32165620578, "target": { "key": "1cbe6f5a21858a8d40778893611695e2bf51d5f78e6b3882b6f2af525de53fe1" } } ], "extra": [ 1, 147, 185, 153, 65, 174, 150, 186, 253, 251, 214, 168, 68, 128, 202, 209, 41, 141, 116, 200, 144, 248, 160, 152, 90, 216, 38, 213, 176, 178, 64, 13, 92, 2, 17, 0, 0, 0, 17, 246, 204, 20, 48, 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