Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c6f0ec892c9d09c6a939960050f4521a34480570364969a6b9bc34e7ec1260d

Tx prefix hash: 1de1cc333ce2949b929832c88b7f2249d7f3ce88218a583ca0a65b46002f5806
Tx public key: bbc3eac956635408746a510b412e1b825bd08d3e8cf66b4b261d8654dcccdcb9
Timestamp: 1638733524 Timestamp [UCT]: 2021-12-05 19:45:24 Age [y:d:h:m:s]: 03:329:23:19:44
Block: 389156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1012258 RingCT/type: yes/0
Extra: 01bbc3eac956635408746a510b412e1b825bd08d3e8cf66b4b261d8654dcccdcb9021100000012f6cc1430000000000000000000

1 output(s) for total of 31.518460245000 dcy

stealth address amount amount idx
00: 391a7dfa89084f2a80b1b0ed32ff8c8956ea0be25103b13b3ea294008f03931a 31.518460245000 784185 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": 389166, "vin": [ { "gen": { "height": 389156 } } ], "vout": [ { "amount": 31518460245, "target": { "key": "391a7dfa89084f2a80b1b0ed32ff8c8956ea0be25103b13b3ea294008f03931a" } } ], "extra": [ 1, 187, 195, 234, 201, 86, 99, 84, 8, 116, 106, 81, 11, 65, 46, 27, 130, 91, 208, 141, 62, 140, 246, 107, 75, 38, 29, 134, 84, 220, 204, 220, 185, 2, 17, 0, 0, 0, 18, 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