Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06f52557b536976616a3f9cbf1f73d8a7b7a5a835dde7e994324de2ddee3ff70

Tx prefix hash: 7183f3acb3156e66aa32b111ba851b73697d60ce26fb11861aef35b80f51af74
Tx public key: 627afd123d0d2b5ca50a723f524cbd1af568f629dde5f13ef09153b0e0eb3514
Timestamp: 1710226395 Timestamp [UCT]: 2024-03-12 06:53:15 Age [y:d:h:m:s]: 01:021:20:01:06
Block: 976540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276574 RingCT/type: yes/0
Extra: 01627afd123d0d2b5ca50a723f524cbd1af568f629dde5f13ef09153b0e0eb35140211000000120011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a22c44e1df4f55be2bedf9a9f048728de1ab5f2b9a4013abd1db02700b8a22a 0.600000000000 1436535 of 15

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": 976550, "vin": [ { "gen": { "height": 976540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a22c44e1df4f55be2bedf9a9f048728de1ab5f2b9a4013abd1db02700b8a22a" } } ], "extra": [ 1, 98, 122, 253, 18, 61, 13, 43, 92, 165, 10, 114, 63, 82, 76, 189, 26, 245, 104, 246, 41, 221, 229, 241, 62, 240, 145, 83, 176, 224, 235, 53, 20, 2, 17, 0, 0, 0, 18, 0, 17, 5, 91, 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