Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 513dd4eeb98fdb5cd8d99e803c43d80617b153acb42c74cfd1070b008bf01a31

Tx prefix hash: 78aa95b2ffddc6e52b20247e2a75f122516e46c5d5d43a156968ed38393c9c29
Tx public key: 4112a56238e359c99a6014c4949bab0f4de7c06d0732a7b15c3541b5d9d8b82c
Timestamp: 1711553477 Timestamp [UCT]: 2024-03-27 15:31:17 Age [y:d:h:m:s]: 01:062:04:36:14
Block: 987553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305438 RingCT/type: yes/0
Extra: 014112a56238e359c99a6014c4949bab0f4de7c06d0732a7b15c3541b5d9d8b82c0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80ab41f07cd3bdcf79660f67839188dc4e292f2c789d1064103d807138e5474f 0.600000000000 1447806 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": 987563, "vin": [ { "gen": { "height": 987553 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80ab41f07cd3bdcf79660f67839188dc4e292f2c789d1064103d807138e5474f" } } ], "extra": [ 1, 65, 18, 165, 98, 56, 227, 89, 201, 154, 96, 20, 196, 148, 155, 171, 15, 77, 231, 192, 109, 7, 50, 167, 177, 92, 53, 65, 181, 217, 216, 184, 44, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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