Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7a6bda1015f1fd58b304479a7b4ff6acf5760d36680eee1eefda6c7491fdd63

Tx prefix hash: a2f985641f0204689ae4e3992aab75f89339259d02611b382fd0d688c5f507bc
Tx public key: 1e7d081419ed0c3f66e48562b8f06dc158d63836f6d40b6675b3e355596301ed
Timestamp: 1682283621 Timestamp [UCT]: 2023-04-23 21:00:21 Age [y:d:h:m:s]: 01:348:12:05:59
Block: 745120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 510330 RingCT/type: yes/0
Extra: 011e7d081419ed0c3f66e48562b8f06dc158d63836f6d40b6675b3e355596301ed021100000001b3164c24000000000000000000

1 output(s) for total of 2.085010931000 dcy

stealth address amount amount idx
00: c8da954f88998c10d34e2b2a799d38e5dd3816881a9b91517465f779ccf7f5a1 2.085010931000 1192539 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": 745130, "vin": [ { "gen": { "height": 745120 } } ], "vout": [ { "amount": 2085010931, "target": { "key": "c8da954f88998c10d34e2b2a799d38e5dd3816881a9b91517465f779ccf7f5a1" } } ], "extra": [ 1, 30, 125, 8, 20, 25, 237, 12, 63, 102, 228, 133, 98, 184, 240, 109, 193, 88, 214, 56, 54, 246, 212, 11, 102, 117, 179, 227, 85, 89, 99, 1, 237, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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