Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aae2d592c0f455bb81f904275061a25a2b2ba777064fbc7e25466cc6241396ce

Tx prefix hash: 2eda703e447771e229cacd55802723fe2222505686f14f1b6f554e9d16abd068
Tx public key: f38b6a9a307b334d754d0b01cc06470435204cb1ab63f8a66203a9f23e5ff6d6
Timestamp: 1701702547 Timestamp [UCT]: 2023-12-04 15:09:07 Age [y:d:h:m:s]: 01:084:23:16:44
Block: 905854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321855 RingCT/type: yes/0
Extra: 01f38b6a9a307b334d754d0b01cc06470435204cb1ab63f8a66203a9f23e5ff6d602110000000233af99f4000000000000000000

1 output(s) for total of 0.611687541000 dcy

stealth address amount amount idx
00: 537f60b77564221a780488ca769c094b3cb6e286d35545957ba055dea35c9fdd 0.611687541000 1362771 of 0

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": 905864, "vin": [ { "gen": { "height": 905854 } } ], "vout": [ { "amount": 611687541, "target": { "key": "537f60b77564221a780488ca769c094b3cb6e286d35545957ba055dea35c9fdd" } } ], "extra": [ 1, 243, 139, 106, 154, 48, 123, 51, 77, 117, 77, 11, 1, 204, 6, 71, 4, 53, 32, 76, 177, 171, 99, 248, 166, 98, 3, 169, 242, 62, 95, 246, 214, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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