Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 484ceb01e1183d741d33d5e049426733109e231cd091468ecbe33c073a575aea

Tx prefix hash: 7eb3ba3d7f41a76fd561694d8ac4afdda94034aed57d28665266b609094e582f
Tx public key: 5656e48712e0972da2fbdfd31b7da9713e7cc8a36e8f2a74d811acc85c138a32
Timestamp: 1711288789 Timestamp [UCT]: 2024-03-24 13:59:49 Age [y:d:h:m:s]: 01:229:13:04:54
Block: 985357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422722 RingCT/type: yes/0
Extra: 015656e48712e0972da2fbdfd31b7da9713e7cc8a36e8f2a74d811acc85c138a320211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee3b1c385335fad47bbeab536cbbbf995c64a0aea54a76d80bb3eeb179faa471 0.600000000000 1445566 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": 985367, "vin": [ { "gen": { "height": 985357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee3b1c385335fad47bbeab536cbbbf995c64a0aea54a76d80bb3eeb179faa471" } } ], "extra": [ 1, 86, 86, 228, 135, 18, 224, 151, 45, 162, 251, 223, 211, 27, 125, 169, 113, 62, 124, 200, 163, 110, 143, 42, 116, 216, 17, 172, 200, 92, 19, 138, 50, 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