Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd581d11ee5d08409dafc16262c5e2f843c443601b85e019ba2ea7b9af0450b9

Tx prefix hash: 6514319597cad88d9efaa55554fbc42601b409a3584e3b65e8871faa69543b88
Tx public key: 53f8b19528050f1437410b9e79b91040d9c413a62777e79d182d6ace1bc4052b
Timestamp: 1578457214 Timestamp [UCT]: 2020-01-08 04:20:14 Age [y:d:h:m:s]: 05:047:19:18:51
Block: 40962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1184146 RingCT/type: yes/0
Extra: 0153f8b19528050f1437410b9e79b91040d9c413a62777e79d182d6ace1bc4052b0211000000012264afe6000000000000000000

1 output(s) for total of 449.082355384000 dcy

stealth address amount amount idx
00: fd1d68e5f0d5211cd02e38bb212c7362fd67719fc33aefcf9e8dbe6a19167ee4 449.082355384000 72496 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": 40972, "vin": [ { "gen": { "height": 40962 } } ], "vout": [ { "amount": 449082355384, "target": { "key": "fd1d68e5f0d5211cd02e38bb212c7362fd67719fc33aefcf9e8dbe6a19167ee4" } } ], "extra": [ 1, 83, 248, 177, 149, 40, 5, 15, 20, 55, 65, 11, 158, 121, 185, 16, 64, 217, 196, 19, 166, 39, 119, 231, 157, 24, 45, 106, 206, 27, 196, 5, 43, 2, 17, 0, 0, 0, 1, 34, 100, 175, 230, 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