Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77ad546c9d0151074800916670763f2b55d99f33355bbf9eef1a2360f91d7723

Tx prefix hash: 006afa1a3848c5e3a16a952bc9450aa6a4223faa8d98e3e3c8283d360027cddd
Tx public key: 0a4ea2650db9d7aa2e8652b3170d7d0525107bf3201adc502369bf9abd73d316
Timestamp: 1617510362 Timestamp [UCT]: 2021-04-04 04:26:02 Age [y:d:h:m:s]: 03:304:14:19:21
Block: 232851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 977112 RingCT/type: yes/0
Extra: 010a4ea2650db9d7aa2e8652b3170d7d0525107bf3201adc502369bf9abd73d31602110000003d0dc70aa7000000000000000000

1 output(s) for total of 103.864839270000 dcy

stealth address amount amount idx
00: 29f6b29695de0766ad8243ee075648feb898994df297264805b1aa36811e75e5 103.864839270000 483695 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": 232861, "vin": [ { "gen": { "height": 232851 } } ], "vout": [ { "amount": 103864839270, "target": { "key": "29f6b29695de0766ad8243ee075648feb898994df297264805b1aa36811e75e5" } } ], "extra": [ 1, 10, 78, 162, 101, 13, 185, 215, 170, 46, 134, 82, 179, 23, 13, 125, 5, 37, 16, 123, 243, 32, 26, 220, 80, 35, 105, 191, 154, 189, 115, 211, 22, 2, 17, 0, 0, 0, 61, 13, 199, 10, 167, 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