Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22104140ed6b4bb0481a1cc684c1e7ece0c76ca7b0bb8b103639fbd2163425de

Tx prefix hash: c0993869a5d1dcf5371f03d049fe235d4e2f1f46fd3f2208b54286fe8dda3b18
Tx public key: 1a60967a43e29f8d0e9f7e5c2dee1ddb418e30a1e5783a503389b18a5c7d7b89
Timestamp: 1578776181 Timestamp [UCT]: 2020-01-11 20:56:21 Age [y:d:h:m:s]: 05:294:17:47:30
Block: 43424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1358569 RingCT/type: yes/0
Extra: 011a60967a43e29f8d0e9f7e5c2dee1ddb418e30a1e5783a503389b18a5c7d7b8902110000000b8a2ee0d9000000000000000000

1 output(s) for total of 440.675701431000 dcy

stealth address amount amount idx
00: 080cc887f47111db02b4e3328396f8cce06166bbef1490797a40c8cb1a4b54f8 440.675701431000 78657 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": 43434, "vin": [ { "gen": { "height": 43424 } } ], "vout": [ { "amount": 440675701431, "target": { "key": "080cc887f47111db02b4e3328396f8cce06166bbef1490797a40c8cb1a4b54f8" } } ], "extra": [ 1, 26, 96, 150, 122, 67, 226, 159, 141, 14, 159, 126, 92, 45, 238, 29, 219, 65, 142, 48, 161, 229, 120, 58, 80, 51, 137, 177, 138, 92, 125, 123, 137, 2, 17, 0, 0, 0, 11, 138, 46, 224, 217, 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