Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13518bd826eb2bdc3c767d7018c783227e0107bf93f24836275911398278e8d0

Tx prefix hash: 6e4016be184ebb6a16e703c26d7cf3358b96d5ddcc783d404faaeab61c5bf98c
Tx public key: 5a5c018f08baaa0290ea2944fd9bd966f2493724d70cc6f619bb74b9f47a6e9e
Timestamp: 1687015795 Timestamp [UCT]: 2023-06-17 15:29:55 Age [y:d:h:m:s]: 01:206:16:15:16
Block: 784356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 409098 RingCT/type: yes/0
Extra: 015a5c018f08baaa0290ea2944fd9bd966f2493724d70cc6f619bb74b9f47a6e9e021100000004faf35c9c000000000000000000

1 output(s) for total of 1.545621403000 dcy

stealth address amount amount idx
00: b4b90defad1300342870dcac05c1ef0e7e53cd5033be435a005f87519ff0e4be 1.545621403000 1234243 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": 784366, "vin": [ { "gen": { "height": 784356 } } ], "vout": [ { "amount": 1545621403, "target": { "key": "b4b90defad1300342870dcac05c1ef0e7e53cd5033be435a005f87519ff0e4be" } } ], "extra": [ 1, 90, 92, 1, 143, 8, 186, 170, 2, 144, 234, 41, 68, 253, 155, 217, 102, 242, 73, 55, 36, 215, 12, 198, 246, 25, 187, 116, 185, 244, 122, 110, 158, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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