Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39207cb3939616ab273a33f64bc76a070d84b9cf992109d11be17b7f2d51a76b

Tx prefix hash: 02e581ad3e35f56ea8f84f90db5bddd8f7768bd4f4c5ddf9fded69e67ab4940d
Tx public key: 422c79ba5efe79b5739def3b25e80b9ac2f8617b64bb0ab716c41d4a95120178
Timestamp: 1674653480 Timestamp [UCT]: 2023-01-25 13:31:20 Age [y:d:h:m:s]: 02:071:22:38:24
Block: 682490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 573049 RingCT/type: yes/0
Extra: 01422c79ba5efe79b5739def3b25e80b9ac2f8617b64bb0ab716c41d4a951201780211000000035029cbac000000000000000000

1 output(s) for total of 3.362228722000 dcy

stealth address amount amount idx
00: 525576014d289ae54f116df395331c58bc4536f1c6e04885b26d94e7fe820bc1 3.362228722000 1124615 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": 682500, "vin": [ { "gen": { "height": 682490 } } ], "vout": [ { "amount": 3362228722, "target": { "key": "525576014d289ae54f116df395331c58bc4536f1c6e04885b26d94e7fe820bc1" } } ], "extra": [ 1, 66, 44, 121, 186, 94, 254, 121, 181, 115, 157, 239, 59, 37, 232, 11, 154, 194, 248, 97, 123, 100, 187, 10, 183, 22, 196, 29, 74, 149, 18, 1, 120, 2, 17, 0, 0, 0, 3, 80, 41, 203, 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