Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5932b5060171a398cc7bd6c03555389a617a70ec988a1e8cf26ec1614540867a

Tx prefix hash: cc9d1af39311f81e8adee7c2af2f964757474fc1dd275f96d44ad96a618a8a7e
Tx public key: 27e654275cb24983b6c4fe511cb14466bf2b3d4657d3a02c34aef6c7fbefe09a
Timestamp: 1696693635 Timestamp [UCT]: 2023-10-07 15:47:15 Age [y:d:h:m:s]: 01:101:07:09:37
Block: 864534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333657 RingCT/type: yes/0
Extra: 0127e654275cb24983b6c4fe511cb14466bf2b3d4657d3a02c34aef6c7fbefe09a02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.838378260000 dcy

stealth address amount amount idx
00: e84c3cfbe998c57ac125933b240c3c626b8967927a0c5a3dd9d5bfc7267018b2 0.838378260000 1319050 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": 864544, "vin": [ { "gen": { "height": 864534 } } ], "vout": [ { "amount": 838378260, "target": { "key": "e84c3cfbe998c57ac125933b240c3c626b8967927a0c5a3dd9d5bfc7267018b2" } } ], "extra": [ 1, 39, 230, 84, 39, 92, 178, 73, 131, 182, 196, 254, 81, 28, 177, 68, 102, 191, 43, 61, 70, 87, 211, 160, 44, 52, 174, 246, 199, 251, 239, 224, 154, 2, 17, 0, 0, 0, 5, 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