Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 387f67f59c4da96a0e698dc4f0d37a1c2720e605b2e591799642b504e32c142a

Tx prefix hash: ae1f467110ad299ce9d3ed1cb6c17aeea8e58ac9b8b8523425fdd9309f387d69
Tx public key: a538cd4e369ab956be42fa9003f6fff4e4f48b49f2367aea131662b2ca941a3a
Timestamp: 1672164011 Timestamp [UCT]: 2022-12-27 18:00:11 Age [y:d:h:m:s]: 02:022:13:50:40
Block: 661839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 538055 RingCT/type: yes/0
Extra: 01a538cd4e369ab956be42fa9003f6fff4e4f48b49f2367aea131662b2ca941a3a021100000001e7ace25d000000000000000000

1 output(s) for total of 3.935977614000 dcy

stealth address amount amount idx
00: a8f71bbb4f7b72f0910a91d4310fc11b7e9b1cfce6abb417528d0f48a4bdb9e6 3.935977614000 1102652 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": 661849, "vin": [ { "gen": { "height": 661839 } } ], "vout": [ { "amount": 3935977614, "target": { "key": "a8f71bbb4f7b72f0910a91d4310fc11b7e9b1cfce6abb417528d0f48a4bdb9e6" } } ], "extra": [ 1, 165, 56, 205, 78, 54, 154, 185, 86, 190, 66, 250, 144, 3, 246, 255, 244, 228, 244, 139, 73, 242, 54, 122, 234, 19, 22, 98, 178, 202, 148, 26, 58, 2, 17, 0, 0, 0, 1, 231, 172, 226, 93, 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