Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e3a577157695f07197587b1b8f19faefd97659373dee183e87b3a022ed01299

Tx prefix hash: 69323af724b17453956ae31c6e7ddcac97c2b0fcd962782c28c5013f61f3cbd7
Tx public key: 404fad23e6eff0995b5f80385b4857f9a6460b5a2ef85183a2ec30a3c7ef5d5d
Timestamp: 1645390703 Timestamp [UCT]: 2022-02-20 20:58:23 Age [y:d:h:m:s]: 02:284:09:37:35
Block: 442866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 722666 RingCT/type: yes/0
Extra: 01404fad23e6eff0995b5f80385b4857f9a6460b5a2ef85183a2ec30a3c7ef5d5d02110000000106faf294000000000000000000

1 output(s) for total of 20.921912854000 dcy

stealth address amount amount idx
00: aa0a0fbbc2e0457cc5ad08bb596081d3fcb81a4b1274779b5c1bdc010dc0449e 20.921912854000 855753 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": 442876, "vin": [ { "gen": { "height": 442866 } } ], "vout": [ { "amount": 20921912854, "target": { "key": "aa0a0fbbc2e0457cc5ad08bb596081d3fcb81a4b1274779b5c1bdc010dc0449e" } } ], "extra": [ 1, 64, 79, 173, 35, 230, 239, 240, 153, 91, 95, 128, 56, 91, 72, 87, 249, 166, 70, 11, 90, 46, 248, 81, 131, 162, 236, 48, 163, 199, 239, 93, 93, 2, 17, 0, 0, 0, 1, 6, 250, 242, 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