Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed93751463cbd9488e0e68f15a1e87d5eb8aa9ca1b729ce342ddc0d8574c224e

Tx prefix hash: 3b63be406f5e530ac7de9f0ae75a91d03303e90dcad2a232516c4a4de0b27d28
Tx public key: 657c0d263815751e21800ab6391f427a6a5b7aff0ba11ecae859a1e438c88111
Timestamp: 1632848083 Timestamp [UCT]: 2021-09-28 16:54:43 Age [y:d:h:m:s]: 03:090:05:48:47
Block: 342637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 841245 RingCT/type: yes/0
Extra: 01657c0d263815751e21800ab6391f427a6a5b7aff0ba11ecae859a1e438c88111021100000002f60c5d7e000000000000000000

1 output(s) for total of 44.947894314000 dcy

stealth address amount amount idx
00: bb29ee550473ddbee063280646e2064e21d8931cf5df0463c8ceb3846da18936 44.947894314000 703601 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": 342647, "vin": [ { "gen": { "height": 342637 } } ], "vout": [ { "amount": 44947894314, "target": { "key": "bb29ee550473ddbee063280646e2064e21d8931cf5df0463c8ceb3846da18936" } } ], "extra": [ 1, 101, 124, 13, 38, 56, 21, 117, 30, 33, 128, 10, 182, 57, 31, 66, 122, 106, 91, 122, 255, 11, 161, 30, 202, 232, 89, 161, 228, 56, 200, 129, 17, 2, 17, 0, 0, 0, 2, 246, 12, 93, 126, 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