Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 891cf4b4998e112fef90d24bfe6779bb112f6afd3fad232c69d40f45da5911e2

Tx prefix hash: 4b17687373b182bfcf1a99a9bb2ce18b53cc89529e6b281dab63947b04fc56a8
Tx public key: af1f754eba7e8c6966dbb4502f0d6f465b2d4249061592d8ff78db02ebf84727
Timestamp: 1703347108 Timestamp [UCT]: 2023-12-23 15:58:28 Age [y:d:h:m:s]: 01:364:07:35:16
Block: 919490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 519274 RingCT/type: yes/0
Extra: 01af1f754eba7e8c6966dbb4502f0d6f465b2d4249061592d8ff78db02ebf847270211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58fb30a80be633e2b2ae6cac3135d4fc9998d02b626fad4d9cff96f5b6f3639f 0.600000000000 1377164 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": 919500, "vin": [ { "gen": { "height": 919490 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58fb30a80be633e2b2ae6cac3135d4fc9998d02b626fad4d9cff96f5b6f3639f" } } ], "extra": [ 1, 175, 31, 117, 78, 186, 126, 140, 105, 102, 219, 180, 80, 47, 13, 111, 70, 91, 45, 66, 73, 6, 21, 146, 216, 255, 120, 219, 2, 235, 248, 71, 39, 2, 17, 0, 0, 0, 4, 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