Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de8b14b8f56d6b35fef5a1c4a6b736a7f51036e9ceae3279c0e749523aee02d8

Tx prefix hash: 33cd34be7e67a59b71d980c9e0b3e1a8203eb78632e31d3913c922da4781e4b1
Tx public key: 45169e79079664d2dec323861f34620ff8d706b0a3ba2705a55637bb8f06ae67
Timestamp: 1704251522 Timestamp [UCT]: 2024-01-03 03:12:02 Age [y:d:h:m:s]: 01:127:19:39:41
Block: 926985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352481 RingCT/type: yes/0
Extra: 0145169e79079664d2dec323861f34620ff8d706b0a3ba2705a55637bb8f06ae670211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6093313c168e01b202ef97951d4e8f74c2af856f0617a774b770b1419fede318 0.600000000000 1384785 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": 926995, "vin": [ { "gen": { "height": 926985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6093313c168e01b202ef97951d4e8f74c2af856f0617a774b770b1419fede318" } } ], "extra": [ 1, 69, 22, 158, 121, 7, 150, 100, 210, 222, 195, 35, 134, 31, 52, 98, 15, 248, 215, 6, 176, 163, 186, 39, 5, 165, 86, 55, 187, 143, 6, 174, 103, 2, 17, 0, 0, 0, 5, 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