Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0995074013f32dd830761c7991a9d9c5a38f5270de31cd0af9989a0a56b5515

Tx prefix hash: 46093cfec0c0bc4956f54bea26f759a615032e5221f9608ebb7dc57f9a1cdc0f
Tx public key: da950b439815c1aaee60bd6b13e5c451e5c8cf70af3c8654aa8776cee3244c56
Timestamp: 1707048260 Timestamp [UCT]: 2024-02-04 12:04:20 Age [y:d:h:m:s]: 00:322:08:38:34
Block: 950163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230838 RingCT/type: yes/0
Extra: 01da950b439815c1aaee60bd6b13e5c451e5c8cf70af3c8654aa8776cee3244c560211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acc7dfe0ecd27a52b6303b2a00ddf5ac1059dcfb8b29f8abe3e9ff09fbcdd496 0.600000000000 1408733 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": 950173, "vin": [ { "gen": { "height": 950163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acc7dfe0ecd27a52b6303b2a00ddf5ac1059dcfb8b29f8abe3e9ff09fbcdd496" } } ], "extra": [ 1, 218, 149, 11, 67, 152, 21, 193, 170, 238, 96, 189, 107, 19, 229, 196, 81, 229, 200, 207, 112, 175, 60, 134, 84, 170, 135, 118, 206, 227, 36, 76, 86, 2, 17, 0, 0, 0, 2, 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