Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe08db2a8151916003a4c7387dbb6dea006b62aac4950a3c849bb8c81f6f86a8

Tx prefix hash: af2ed95386de569bfc436edcb0ae35f649e56e6ea36b1eacca4d9a0d4f7e5be4
Tx public key: 0111ea82b39d6468a9c6c7eeab5fcb4fe6fe34cf0ba65e1899d790465e76286e
Timestamp: 1713188851 Timestamp [UCT]: 2024-04-15 13:47:31 Age [y:d:h:m:s]: 01:230:04:18:20
Block: 1001078 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 423203 RingCT/type: yes/0
Extra: 010111ea82b39d6468a9c6c7eeab5fcb4fe6fe34cf0ba65e1899d790465e76286e0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98426cd8ac8c4a4071110b844957d6680f65b2231982a538d726512ea75c9541 0.600000000000 1461580 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": 1001088, "vin": [ { "gen": { "height": 1001078 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98426cd8ac8c4a4071110b844957d6680f65b2231982a538d726512ea75c9541" } } ], "extra": [ 1, 1, 17, 234, 130, 179, 157, 100, 104, 169, 198, 199, 238, 171, 95, 203, 79, 230, 254, 52, 207, 11, 166, 94, 24, 153, 215, 144, 70, 94, 118, 40, 110, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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