Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa0f6b8fa102c418141a12496f9be253db9cc8452c61308cce5dce8a0ee1d8c9

Tx prefix hash: 9c45a97ccbefccd51ebfe4f190ee258f8104e4da8cf343082980b11aa9e4ebd9
Tx public key: b9f7eaa2ebe7d4cb0532883897cd31c92e81394a0e63b0d2c3c23e56b743a490
Timestamp: 1710540056 Timestamp [UCT]: 2024-03-15 22:00:56 Age [y:d:h:m:s]: 01:061:00:33:12
Block: 979148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304590 RingCT/type: yes/0
Extra: 01b9f7eaa2ebe7d4cb0532883897cd31c92e81394a0e63b0d2c3c23e56b743a4900211000000107a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ad96e40d9ba72e069ca651e9e5b2f0d67bc74a736539c2d0e5ff737d9c48b38 0.600000000000 1439181 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": 979158, "vin": [ { "gen": { "height": 979148 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ad96e40d9ba72e069ca651e9e5b2f0d67bc74a736539c2d0e5ff737d9c48b38" } } ], "extra": [ 1, 185, 247, 234, 162, 235, 231, 212, 203, 5, 50, 136, 56, 151, 205, 49, 201, 46, 129, 57, 74, 14, 99, 176, 210, 195, 194, 62, 86, 183, 67, 164, 144, 2, 17, 0, 0, 0, 16, 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