Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 705558cd1455f1edbc454f2097cc0ce940b60a998ea559192f7f8886e822fb6e

Tx prefix hash: 1c5c792cb1bed9eee98ac5775296f70dfd9a38b23fbe96cff283009b16a666cc
Tx public key: 96a5ec089959ef4c2f5cf5fed089f40cb3ac45c6fd574d5ea5d008b94928bbff
Timestamp: 1715080504 Timestamp [UCT]: 2024-05-07 11:15:04 Age [y:d:h:m:s]: 00:337:09:17:15
Block: 1016772 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241160 RingCT/type: yes/0
Extra: 0196a5ec089959ef4c2f5cf5fed089f40cb3ac45c6fd574d5ea5d008b94928bbff0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 900798d7b9ad7db7efbd12c70d4656610fe05aa8d8bf0dad773e9835adb8ba0f 0.600000000000 1480449 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": 1016782, "vin": [ { "gen": { "height": 1016772 } } ], "vout": [ { "amount": 600000000, "target": { "key": "900798d7b9ad7db7efbd12c70d4656610fe05aa8d8bf0dad773e9835adb8ba0f" } } ], "extra": [ 1, 150, 165, 236, 8, 153, 89, 239, 76, 47, 92, 245, 254, 208, 137, 244, 12, 179, 172, 69, 198, 253, 87, 77, 94, 165, 208, 8, 185, 73, 40, 187, 255, 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