Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc2bfa61ff352d55a6b0b280a16e46d47b2255ace8e7206c3afac06161362cd7

Tx prefix hash: 3d15f793d7d4a01f300c0c1b06d7da7d61c672c53e3ae21b5d8e3351de9f5178
Tx public key: e8e2c943b404d4ddc5943cc3dc9f522d505d790ac330e820eb61a4393460ef71
Timestamp: 1709079521 Timestamp [UCT]: 2024-02-28 00:18:41 Age [y:d:h:m:s]: 01:257:00:56:12
Block: 967027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442429 RingCT/type: yes/0
Extra: 01e8e2c943b404d4ddc5943cc3dc9f522d505d790ac330e820eb61a4393460ef710211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c975e13c8009e6d700547814a9a2d58daf33dce52f886cb9403079260d7597c5 0.600000000000 1426798 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": 967037, "vin": [ { "gen": { "height": 967027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c975e13c8009e6d700547814a9a2d58daf33dce52f886cb9403079260d7597c5" } } ], "extra": [ 1, 232, 226, 201, 67, 180, 4, 212, 221, 197, 148, 60, 195, 220, 159, 82, 45, 80, 93, 121, 10, 195, 48, 232, 32, 235, 97, 164, 57, 52, 96, 239, 113, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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