Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a66f73239d5fb6b83fe0702777dbbb711b0cf5d56558d38dd1b4f09b5d3879c8

Tx prefix hash: 9fa6a2be4ac60643991b6b0fdd4f95caaf99bdb3ec04612ff8751ceed0bdb23c
Tx public key: 16e718223d5cf1ae447ee3feccabb7b882a6254f40b0c28fc6e0c6a0b28ad9ae
Timestamp: 1733888419 Timestamp [UCT]: 2024-12-11 03:40:19 Age [y:d:h:m:s]: 00:108:04:03:13
Block: 1172606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77081 RingCT/type: yes/0
Extra: 0116e718223d5cf1ae447ee3feccabb7b882a6254f40b0c28fc6e0c6a0b28ad9ae021100000001c7ca14c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a176503ee763990d0440a2940d3b94e65ed52a6c84cb9d560c6af771aa55e841 0.600000000000 1658521 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": 1172616, "vin": [ { "gen": { "height": 1172606 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a176503ee763990d0440a2940d3b94e65ed52a6c84cb9d560c6af771aa55e841" } } ], "extra": [ 1, 22, 231, 24, 34, 61, 92, 241, 174, 68, 126, 227, 254, 204, 171, 183, 184, 130, 166, 37, 79, 64, 176, 194, 143, 198, 224, 198, 160, 178, 138, 217, 174, 2, 17, 0, 0, 0, 1, 199, 202, 20, 193, 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