Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7357d429140c2a9d587fc7c3af3a954d9d5caa45a6fb312a065cd4642b442d1d

Tx prefix hash: 7801a5fcfced0364cb6cf818c65eb8e96dfdbc3db6e111b53aa3f216e231df1c
Tx public key: 589db3ea2ac462cba1def3a63d7af962905730e36b83fd13a671eb6b90b1f2fe
Timestamp: 1702726502 Timestamp [UCT]: 2023-12-16 11:35:02 Age [y:d:h:m:s]: 01:117:05:48:14
Block: 914351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344921 RingCT/type: yes/0
Extra: 01589db3ea2ac462cba1def3a63d7af962905730e36b83fd13a671eb6b90b1f2fe02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b761c7bc8e013121b393d809affd3dee65971132b4bc297614eb8ff489e5560b 0.600000000000 1371665 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": 914361, "vin": [ { "gen": { "height": 914351 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b761c7bc8e013121b393d809affd3dee65971132b4bc297614eb8ff489e5560b" } } ], "extra": [ 1, 88, 157, 179, 234, 42, 196, 98, 203, 161, 222, 243, 166, 61, 122, 249, 98, 144, 87, 48, 227, 107, 131, 253, 19, 166, 113, 235, 107, 144, 177, 242, 254, 2, 17, 0, 0, 0, 2, 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