Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 641c33fa060ff7dd360f53c325c93ed4680ce7ab15def37318ec1b7fa3d743a1

Tx prefix hash: 8099c5dcbe5aa409a029a554c10a68e4addeca0ca9381aa32ab3fa3ba80ac41a
Tx public key: 175cf57f0dce35f60be84e8f7039aeb22dd3b02f847b92ae0cd5c8f67c731dd2
Timestamp: 1712796296 Timestamp [UCT]: 2024-04-11 00:44:56 Age [y:d:h:m:s]: 00:163:22:01:51
Block: 997806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117444 RingCT/type: yes/0
Extra: 01175cf57f0dce35f60be84e8f7039aeb22dd3b02f847b92ae0cd5c8f67c731dd202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cbe117f893dde35ea0288d0982381f48a12663c788aa12ef753f2c7169a0646 0.600000000000 1458240 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": 997816, "vin": [ { "gen": { "height": 997806 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cbe117f893dde35ea0288d0982381f48a12663c788aa12ef753f2c7169a0646" } } ], "extra": [ 1, 23, 92, 245, 127, 13, 206, 53, 246, 11, 232, 78, 143, 112, 57, 174, 178, 45, 211, 176, 47, 132, 123, 146, 174, 12, 213, 200, 246, 124, 115, 29, 210, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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