Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f14fef651791701608739b8e24e7d94401e5f7ac97f91b18c4ca7bf7cc4d13f

Tx prefix hash: 816b44b146336eb9b6d2e6404620b65e40f313e26a9a2d7a00cf9a840a2a9870
Tx public key: 701300199bbfb5096e8c78d6f89c90f9c710c34af1eaa1210b5ae8faacdf9b5b
Timestamp: 1674783022 Timestamp [UCT]: 2023-01-27 01:30:22 Age [y:d:h:m:s]: 02:078:13:55:10
Block: 683557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 577809 RingCT/type: yes/0
Extra: 01701300199bbfb5096e8c78d6f89c90f9c710c34af1eaa1210b5ae8faacdf9b5b021100000001e6d27f9c000000000000000000

1 output(s) for total of 3.334969285000 dcy

stealth address amount amount idx
00: 804f36b1341ac289738716b5e51491695387dfe115a9bacb9d7219e4cf62f47e 3.334969285000 1125752 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": 683567, "vin": [ { "gen": { "height": 683557 } } ], "vout": [ { "amount": 3334969285, "target": { "key": "804f36b1341ac289738716b5e51491695387dfe115a9bacb9d7219e4cf62f47e" } } ], "extra": [ 1, 112, 19, 0, 25, 155, 191, 181, 9, 110, 140, 120, 214, 248, 156, 144, 249, 199, 16, 195, 74, 241, 234, 161, 33, 11, 90, 232, 250, 172, 223, 155, 91, 2, 17, 0, 0, 0, 1, 230, 210, 127, 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