Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f647ddfec1b4de6623794b7fae92bfc8bbd88bc468b32e92f8755db090798a7c

Tx prefix hash: c59e3d5e5dbcbdab126b2f9170e3826bd14a488e1c4fe7e289f460aeffbd7b9b
Tx public key: 26829aaa331fcf0ac185098282a9cbc34db1f4a5879c5857ec41a4857c3a556d
Timestamp: 1700978495 Timestamp [UCT]: 2023-11-26 06:01:35 Age [y:d:h:m:s]: 01:347:12:05:23
Block: 899854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 507246 RingCT/type: yes/0
Extra: 0126829aaa331fcf0ac185098282a9cbc34db1f4a5879c5857ec41a4857c3a556d02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.640339267000 dcy

stealth address amount amount idx
00: 47d2b8d87f231d91d5d0e82ea620f2f982ff8901ed3671b3181e581295b60647 0.640339267000 1356321 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": 899864, "vin": [ { "gen": { "height": 899854 } } ], "vout": [ { "amount": 640339267, "target": { "key": "47d2b8d87f231d91d5d0e82ea620f2f982ff8901ed3671b3181e581295b60647" } } ], "extra": [ 1, 38, 130, 154, 170, 51, 31, 207, 10, 193, 133, 9, 130, 130, 169, 203, 195, 77, 177, 244, 165, 135, 156, 88, 87, 236, 65, 164, 133, 124, 58, 85, 109, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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