Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e72a810863a995b950f65c830b9e2381a08b38103bb7a98407cbd49abc1bd5d

Tx prefix hash: 2e028e8c245332e48b4f1ef2f4aed7a7af1af8a89795717a2ba3439ad7745264
Tx public key: 57fc7ab6e484faf879bb5dff91b9b007b913bfedf535d80ba77968cf8ef38633
Timestamp: 1587124852 Timestamp [UCT]: 2020-04-17 12:00:52 Age [y:d:h:m:s]: 04:359:10:44:52
Block: 93175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1165543 RingCT/type: yes/0
Extra: 0157fc7ab6e484faf879bb5dff91b9b007b913bfedf535d80ba77968cf8ef3863302110000000a4943cd9f000000000000000000

1 output(s) for total of 301.495491380000 dcy

stealth address amount amount idx
00: 318b19b412c6a5d5c2f1eee291480bba58046532ecc817b2e5d84549070dc5ae 301.495491380000 166093 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": 93185, "vin": [ { "gen": { "height": 93175 } } ], "vout": [ { "amount": 301495491380, "target": { "key": "318b19b412c6a5d5c2f1eee291480bba58046532ecc817b2e5d84549070dc5ae" } } ], "extra": [ 1, 87, 252, 122, 182, 228, 132, 250, 248, 121, 187, 93, 255, 145, 185, 176, 7, 185, 19, 191, 237, 245, 53, 216, 11, 167, 121, 104, 207, 142, 243, 134, 51, 2, 17, 0, 0, 0, 10, 73, 67, 205, 159, 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