Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a67a4fe07c0f00cd718c66998e90e7ebf3bd20287f3db51f5b49dc4225b9545

Tx prefix hash: b887a0579643d4169abbd37486013f93a27f8ca6c51f82e08e8612b92eedab18
Tx public key: 016feaed27f047b22655f14df6b9d1e24de1ea1e380b192862989190f10d0aa2
Timestamp: 1694865581 Timestamp [UCT]: 2023-09-16 11:59:41 Age [y:d:h:m:s]: 01:129:08:54:45
Block: 849365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353734 RingCT/type: yes/0
Extra: 01016feaed27f047b22655f14df6b9d1e24de1ea1e380b192862989190f10d0aa2021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.941241840000 dcy

stealth address amount amount idx
00: 5e9ca64b597b66a2fa5b84be7e313f4e817b795e446c85c0d203027f4aeb6e05 0.941241840000 1303025 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": 849375, "vin": [ { "gen": { "height": 849365 } } ], "vout": [ { "amount": 941241840, "target": { "key": "5e9ca64b597b66a2fa5b84be7e313f4e817b795e446c85c0d203027f4aeb6e05" } } ], "extra": [ 1, 1, 111, 234, 237, 39, 240, 71, 178, 38, 85, 241, 77, 246, 185, 209, 226, 77, 225, 234, 30, 56, 11, 25, 40, 98, 152, 145, 144, 241, 13, 10, 162, 2, 17, 0, 0, 0, 8, 230, 210, 127, 156, 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