Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a300741485f80214dea4ee35df939a095286947a09c160bb997e35226c22547

Tx prefix hash: cf883d4a334f2a51dca1e87eb37963910ac18c10321373a44f20dc6f4e48f3d9
Tx public key: 380af1692f66af51c9cdff257e881f1bcf2c2472fd5e0348d303c5f47ea633d8
Timestamp: 1703832920 Timestamp [UCT]: 2023-12-29 06:55:20 Age [y:d:h:m:s]: 01:156:02:21:15
Block: 923521 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372723 RingCT/type: yes/0
Extra: 01380af1692f66af51c9cdff257e881f1bcf2c2472fd5e0348d303c5f47ea633d8021100000002ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db22b9baa0abd25e60509a4e42150dd50e5a42aca5bc05f9f4ba5255078bd64e 0.600000000000 1381253 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": 923531, "vin": [ { "gen": { "height": 923521 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db22b9baa0abd25e60509a4e42150dd50e5a42aca5bc05f9f4ba5255078bd64e" } } ], "extra": [ 1, 56, 10, 241, 105, 47, 102, 175, 81, 201, 205, 255, 37, 126, 136, 31, 27, 207, 44, 36, 114, 253, 94, 3, 72, 211, 3, 197, 244, 126, 166, 51, 216, 2, 17, 0, 0, 0, 2, 173, 86, 148, 172, 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