Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46dbf8c10fd73385d3ac6696138882a5bd36c7088783a05e1d9320f68bb2a4bf

Tx prefix hash: a7d4d09e345bcfead6f58cba96f5b40bf438815b4af9f095da8c769908bd7175
Tx public key: 94d395b4b16a61a8e9865a3869f1635611f2f09620799e1aec7e6ec54c12b06c
Timestamp: 1711751550 Timestamp [UCT]: 2024-03-29 22:32:30 Age [y:d:h:m:s]: 01:012:07:25:19
Block: 989190 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269751 RingCT/type: yes/0
Extra: 0194d395b4b16a61a8e9865a3869f1635611f2f09620799e1aec7e6ec54c12b06c0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39e270e1b4acbe1129eecc4a5f65ea8696177f4d9a391e4d426e41171d943d87 0.600000000000 1449485 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": 989200, "vin": [ { "gen": { "height": 989190 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39e270e1b4acbe1129eecc4a5f65ea8696177f4d9a391e4d426e41171d943d87" } } ], "extra": [ 1, 148, 211, 149, 180, 177, 106, 97, 168, 233, 134, 90, 56, 105, 241, 99, 86, 17, 242, 240, 150, 32, 121, 158, 26, 236, 126, 110, 197, 76, 18, 176, 108, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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