Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe31b183be25c2e7ca1a2b2d54e5444786698930269d38ffdc1af9c65d4c8244

Tx prefix hash: 21aea82fd2f8c245b97cdd9fa85cbf081d0488421c23e70707503f078d05f80c
Tx public key: 02a57a1eefedb57722ea7cad8a9ce869f97aca272cb347e26cef47f4ea4ec333
Timestamp: 1694650623 Timestamp [UCT]: 2023-09-14 00:17:03 Age [y:d:h:m:s]: 01:253:16:42:31
Block: 847579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442456 RingCT/type: yes/0
Extra: 0102a57a1eefedb57722ea7cad8a9ce869f97aca272cb347e26cef47f4ea4ec33302110000000333af99f4000000000000000000

1 output(s) for total of 0.954155123000 dcy

stealth address amount amount idx
00: ced571af90018cb0a6fae0826d5a22030f1135586bf5cfc4e75f2eee1226c174 0.954155123000 1301109 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": 847589, "vin": [ { "gen": { "height": 847579 } } ], "vout": [ { "amount": 954155123, "target": { "key": "ced571af90018cb0a6fae0826d5a22030f1135586bf5cfc4e75f2eee1226c174" } } ], "extra": [ 1, 2, 165, 122, 30, 239, 237, 181, 119, 34, 234, 124, 173, 138, 156, 232, 105, 249, 122, 202, 39, 44, 179, 71, 226, 108, 239, 71, 244, 234, 78, 195, 51, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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