Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58b7231d266d35b1c045b94160eab281d3a5d89f6491b331e2d37435bead8ab9

Tx prefix hash: 4a56c2d4a455c378ff0f5b609bc72eea4f9233595c31b4720ebdb383bcb56f7b
Tx public key: c80a2871908b62b0769d5d8ad3620f21b9d4e95d01106e821acf5d13cb17f4b2
Timestamp: 1706897464 Timestamp [UCT]: 2024-02-02 18:11:04 Age [y:d:h:m:s]: 01:061:07:21:30
Block: 948915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304878 RingCT/type: yes/0
Extra: 01c80a2871908b62b0769d5d8ad3620f21b9d4e95d01106e821acf5d13cb17f4b202110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 764a801c35be0e3b8840706a5ef73bc54b59fea2211d9e0f895dae4f8965fabb 0.600000000000 1407427 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": 948925, "vin": [ { "gen": { "height": 948915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "764a801c35be0e3b8840706a5ef73bc54b59fea2211d9e0f895dae4f8965fabb" } } ], "extra": [ 1, 200, 10, 40, 113, 144, 139, 98, 176, 118, 157, 93, 138, 211, 98, 15, 33, 185, 212, 233, 93, 1, 16, 110, 130, 26, 207, 93, 19, 203, 23, 244, 178, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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