Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa4e73b7dd544dc84e49082a66f09df156beecd3e894456e21e49826272a4a44

Tx prefix hash: 61e2a42af7192eacc08a0b8cc0150845bd7b473de8680027dac2c45c8166589e
Tx public key: 725380f09a843c9682797de4df92e9d82c6a38cc4a7f4b4edbd741705600ef15
Timestamp: 1731879662 Timestamp [UCT]: 2024-11-17 21:41:02 Age [y:d:h:m:s]: 00:209:13:52:12
Block: 1155960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149545 RingCT/type: yes/0
Extra: 01725380f09a843c9682797de4df92e9d82c6a38cc4a7f4b4edbd741705600ef15021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1778a72e24619b54f9a30bb4af9e59befe2950e198fd541b0d48daad8f39f810 0.600000000000 1641579 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": 1155970, "vin": [ { "gen": { "height": 1155960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1778a72e24619b54f9a30bb4af9e59befe2950e198fd541b0d48daad8f39f810" } } ], "extra": [ 1, 114, 83, 128, 240, 154, 132, 60, 150, 130, 121, 125, 228, 223, 146, 233, 216, 44, 106, 56, 204, 74, 127, 75, 78, 219, 215, 65, 112, 86, 0, 239, 21, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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