Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88908b10f8c502f733846f380e005f59db48ab073053a915ac45593822494223

Tx prefix hash: 08cedf63d7c8020853639d9a2208fe0bbc3d45a9b8647dcc0fbf8932719b83b5
Tx public key: 94c21c539d44f42c80f7f6a40ca30017d0e82dfd8f9edabd9a78e4f76e27f7dc
Timestamp: 1716026056 Timestamp [UCT]: 2024-05-18 09:54:16 Age [y:d:h:m:s]: 01:185:11:04:08
Block: 1024612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391166 RingCT/type: yes/0
Extra: 0194c21c539d44f42c80f7f6a40ca30017d0e82dfd8f9edabd9a78e4f76e27f7dc0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06bff108e07c3be638e061c405912940a649523ed97569bf41acc99133eb6d09 0.600000000000 1490483 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": 1024622, "vin": [ { "gen": { "height": 1024612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06bff108e07c3be638e061c405912940a649523ed97569bf41acc99133eb6d09" } } ], "extra": [ 1, 148, 194, 28, 83, 157, 68, 244, 44, 128, 247, 246, 164, 12, 163, 0, 23, 208, 232, 45, 253, 143, 158, 218, 189, 154, 120, 228, 247, 110, 39, 247, 220, 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