Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f2f04e788c16e3e89e359cc4c96e0356521194de5dd23a1c7055d5dc47fb3eb

Tx prefix hash: 23f68d6c381de1f8e3310be722e2d33fe278e6c857f8f0a58714ee00c84cf206
Tx public key: a175fd36ed03366e41f8f720771765e72d9deedf98dc72e88a5217c8311adb5f
Timestamp: 1656004265 Timestamp [UCT]: 2022-06-23 17:11:05 Age [y:d:h:m:s]: 02:309:22:43:53
Block: 528765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 742640 RingCT/type: yes/0
Extra: 01a175fd36ed03366e41f8f720771765e72d9deedf98dc72e88a5217c8311adb5f02110000000233af99f4000000000000000000

1 output(s) for total of 10.863811403000 dcy

stealth address amount amount idx
00: 64b4e9884ccd8d3b8d016c3a5ccdbf5bab6d24ba91da5967b2ee176f751ceeb2 10.863811403000 957624 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": 528775, "vin": [ { "gen": { "height": 528765 } } ], "vout": [ { "amount": 10863811403, "target": { "key": "64b4e9884ccd8d3b8d016c3a5ccdbf5bab6d24ba91da5967b2ee176f751ceeb2" } } ], "extra": [ 1, 161, 117, 253, 54, 237, 3, 54, 110, 65, 248, 247, 32, 119, 23, 101, 231, 45, 157, 238, 223, 152, 220, 114, 232, 138, 82, 23, 200, 49, 26, 219, 95, 2, 17, 0, 0, 0, 2, 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